-
Notifications
You must be signed in to change notification settings - Fork 127
Scala 2.12.0-RC1 support. #177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
As per gitter chat, I will re-introduce 2.10 to this PR so we can now cover 2.10. 2.11 and 2.12. I've donw the work already, but I really need to restructure some bit. Just a heads-up on what I'm doing |
Done. Here is a git diff https://gist.github.com/BennyHill/401b44ee62f123f23b52ad56d98e5db3 Or I could push tp @paulp 's repo branch, but the changes are done. |
@BennyHill I applied your patch. |
@paulp 👍 |
Thanks for the PR @paulp @BennyHill |
@sksamuel Where is the 1.2 branch? Can we get it out and then release a 1.3-RC1 to get all of @paulp and @BennyHill s changes in? |
@gslowikowski has it locally. |
I will start merging changes today |
👍 |
…ly with 2.11). Details: - sbt version upgraded from 2.13.11 to 2.13.12, - scala version upgraded from 2.11.7 to 2.11.8, - scalatest version upgraded from 3.0.0-M15 to 3.0.0, - unneeded 'javaOptions += "-XX:MaxMetaspaceSize=2048m' settings removed from build, - unneeded EnvSupport class removed from build, - tests made compatible with Scala 2.10, - TravisCI configured for Scala 2.10.6 and 2.11.8. Some fixes borrowed (with modifications) from scoverage#177, thank you @paulp and @BennyHill.
I've just created and merged #179. This PR has conflicts now. I would like it to be split into separated PRs for:
Will you prepare there PRs or should I do it myself? |
All the changes in my original PR (41784d8) are to work with scala 2.12. In some cases "build improvement" was the most expeditious route to that goal. |
There is no |
@gslowikowski From gitter:
This lib is only used as a test-case, not for real logging. Hence we thought best to ditch it. |
If you think it's not needed, we can remove it. |
Some code (required to run tests on Scala 2.10) from this PR was already copied by me and merged. I would like to see two separate PRs created from this one:
Can you do it? |
Some questions from me:
|
I've created #181 with different build improvements, some copied from this PR and a proposal of "clean" Scala 2.12 support introducing changes in this branch (one commit). I'm waiting for answers to my questions above first. |
I'm going to defer to others here. |
@sksamuel, can you take a look and try to answer my questions above? |
@gslowikowski There is definately a jvm phase in 2.11 - type |
@rorygraves Correct, the line which @gslowikowski linked to // val jvmPhase = phaseNamed("jvm") has no bearing on the existence of the phase. |
I've updaged my branch https://github.com/gslowikowski/scalac-scoverage-plugin/commits/scala212-simplified-proposal |
Can you update this PR? Restore these two accidentally removed tests: scalac-scoverage-plugin/scalac-scoverage-plugin/src/test/scala/scoverage/PluginASTSupportTest.scala Lines 79 to 93 in 989329d
scalac-scoverage-plugin/scalac-scoverage-plugin/src/test/scala/scoverage/PluginCoverageTest.scala Lines 288 to 306 in 989329d
|
No, I've put what time into it I can. |
@gslowikowski based on the the fact that half of these changes have been picked/merged separately I suggest you close this PR and manually import any other changes you are going to take. |
@rorygraves I didn't want to take this PR over, but at the end created #182 from my branch (which I hoped would serve for discussion about improving this one). There are still areas for test harness improvements, but new release is more desired now. Improvements can be made at any time later. |
No description provided.